Assigning an IMS control function instance to an IMS endpoint

ABSTRACT

An assignment controller ( 160 ) identifies multiple instances of an IMS control function ( 210, 220 ) as being candidates for assigning to an IMS endpoint ( 110 ). The controller ( 160 ) also obtains a performance metric for each candidate instance that is a measure of the extent to which performance requirements for a signaling path of an anticipated or ongoing session of the endpoint ( 110 ) would be met if the instance were to be assigned to the endpoint ( 110 ). The controller ( 160 ) further obtains an emission metric for each candidate instance that is a measure of the extent to which the instance would produce greenhouse gas emissions if the instance were to be assigned to the endpoint ( 110 ), given the energy consumption and rate of emissions currently attributable to the instance ( 110 ). The controller ( 160 ) prioritizes the candidate instances based on these metrics, and controls assignment of one of the instances to the IMS endpoint ( 110 ) to be performed according to that prioritization.

TECHNICAL FIELD

The present application generally relates to an Internet Protocol (IP)Multimedia Subsystem (IMS), and specifically relates to assigning IMScontrol function instances to IMS endpoints.

BACKGROUND

An Internet Protocol (IP) Multimedia Subsystem (IMS) is an IPconnectivity and service control architecture that enables various typesof media services to be provided to IMS endpoints using commonInternet-based protocols. The IMS is access-independent in the sensethat it can use access networks of various types to transport mediasignaling and bearer traffic. Once an IMS endpoint registers with an IMSnetwork so as to inform the IMS network that it is ready to make andreceive session requests, it can both initiate and terminate sessionsfor any type of media service.

The IMS architecture is defined in terms of functional entities (orsimply “functions”). Functions constitute applications that are executedby a physical host or server. Different types of functions are logicallygrouped into separate layers or planes. The IMS media plane includesfunctions that actually transport and deliver media services so as tohandle content traffic. The IMS control plane, by contrast, includesfunctions that control the media services so as to handle signalingtraffic. The control plane for example includes functions that registeran IMS endpoint with the IMS network and that control the establishment,maintenance, or tearing down of sessions. Exemplary IMS controlfunctions in this regard include a Proxy Call Session Control Function(P-CSCF), an Interrogating Call Session Control Function (I-CSCF), and aServing Call Session Control Function (S-CSCF). Other IMS controlfunctions include a media resource function controller (MRFC) and amedia gateway controller function (MGCF). See 3GPP TS 23.228 v13.0.0,incorporated by reference herein, for details about these well-known IMScontrol functions.

An operator of an IMS network may deploy multiple instances of the sameIMS control function in the network to realize advantages such asincreased signaling capacity, quality of service, and/or redundancy.Deploying multiple instances of the S-CSCF and/or P-CSCF for instanceallows the IMS network operator to better handle peaks in the number ofmedia sessions established. When the multiple S-CSCF and/or P-CSCFinstances are deployed on hosts geographically distributed throughoutthe IMS network, the instance deployed on a host that is physicallyclosest to an IMS endpoint will reduce the latency of the signaling pathfor that IMS endpoint.

Deploying multiple instances of the same IMS control function introducescomplexities to the IMS network because the network must dynamicallydecide which instance to assign to a particular IMS endpoint. Knownapproaches focus on assigning the instance that will balance the loadacross the instances and/or their physical hosts, that providesresiliency to instance and/or host failure, and/or that isgeographically closest to the IMS endpoint so as to minimize theend-to-end signaling delay. Tirana, P. & Medhi, D. (2010), Distributedapproaches to S-CSCF selection in an IMS network., in ‘NOMS’, IEEE, pp.224-231. These known approaches, however, fail to account for factorsthat dictate whether the instance assignment is actually optimal from anenvironmental perspective.

SUMMARY

One or more embodiments herein assign one of multiple IMS controlfunction instances to an IMS endpoint based on the extent to which thoseinstances would produce greenhouse gas emissions if assigned to theendpoint. The embodiments do so by considering the energy consumptionand rate of greenhouse gas emissions that are currently attributable toeach instance, given the type of each energy source being used by thatinstance.

Embodiments for example include a method for governing the assignment ofan IP Multimedia Subsystem, IMS, control function instance to an IMSendpoint. The method includes identifying multiple instances of an IMScontrol function as being candidates for assigning to the IMS endpoint.The method also involves obtaining a performance metric for eachcandidate instance. The performance metric for a candidate instance is ameasure of the extent to which performance requirements (e.g., delayrequirements) for a signaling path of an anticipated or ongoing sessionof the IMS endpoint would be met if the candidate instance were to beassigned to the IMS endpoint. The method further includes obtaining anemission metric for each candidate instance. The emission metric for acandidate instance is a measure of the extent to which the candidateinstance would produce greenhouse gas emissions if the candidateinstance were to be assigned to the IMS endpoint, given the energyconsumption and rate of greenhouse gas emissions currently attributableto the candidate instance. The consumption and rate are dependent on thetype of each energy source (e.g., coal, natural gas, nuclear,hydro-electric, etc.) currently being used by the candidate instance.

With these metrics obtained, the method further includes prioritizingthe candidate instances relative to one another based on the performanceand emission metrics of each instance. The method in this regard morehighly prioritizes candidate instances that would yield higherperformance and lower emissions. Having prioritized the candidateinstances in this way, the method finally involves controllingassignment of one of the candidate instances to the IMS endpoint to beperformed according to this prioritization. By governing instanceassignment in this way, the method in at least some embodimentsadvantageously reduces the overall greenhouse gas emissions of the IMSsystem, e.g., by reducing emissions on an endpoint-by-endpoint orsession-by-session basis.

In some embodiments, the method controls assignment in this way bymanipulating endpoint-specific configuration data that governs theassignment to reflect the prioritization. For example, in oneembodiment, this involves manipulating the endpoint-specificconfiguration data as maintained by at least one of a home subscriberserver, HSS, a dynamic host configuration protocol, DHCP, server, adomain name server, DNS, and a policy server (such as a Policy andCharging Rules Function, PCRF).

In some embodiments, the method is performed periodically oroccasionally in anticipation of the session.

In some embodiments, the assignment is performed during a discoveryprocess (e.g., P-CSCF discovery) in which the IMS endpoint attempts todiscover the IMS control function. In this case, the method is performedat least in part before the discovery process. Alternatively oradditionally, the assignment is performed during a registration processin which the IMS endpoint registers with an IMS. In this case, method isperformed at least in part before the registration process.

In some embodiments, the session is an ongoing session, and two or moreof the candidate instances are virtual instances of the IMS controlfunction in a virtualized IMS. In this case, assignment of one of thecandidate instances to the IMS endpoint comprises changing the instanceassigned to the IMS endpoint from an old virtual instance to a newvirtual instance and migrating a state of the old virtual instance to astate of the new virtual instance to preserve service continuity. In oneor more of these embodiments, controlling instance assignment involvestriggering an IMS management system to perform the assignment (includingmigration) according to the prioritization.

In some embodiments, obtaining the emission metric for a candidateinstance comprises determining the rate of greenhouse gas emissionscurrently attributable to the candidate instance in accordance with adefined policy. The policy in this regard effectively defines differentpossible rates attributable to the candidate instance depending oncertain conditions. The policy specifies those conditions in terms of atleast one of different times of day, different locations of the hardwareexecuting the instance, different types of one or more energy sourcesused by the candidate instance, different types of media for thesession, and, different durations of the session.

In some embodiments, the performance metric for a candidate instance is,at least in part, a measure of the extent to which signaling delayrequirements for the signaling path would be met if the candidateinstance were to be assigned to the IMS endpoint. The delay requirementsin this regard are dependent on a location of the instance relative tothe current location of the IMS endpoint.

In some embodiments, the method further comprises obtaining a billingparameter that indicates whether and/or to what extent the IMS endpointis subscribed to a service providing the prioritized assignment, anddetermining whether or to what extent to perform the method based on thebilling parameter.

In some embodiments, prioritizing is further based on historical dataindicating which of the candidate instances have actually been assignedto the same or a different IMS endpoint in the past.

In some embodiments, the IMS control function is either a proxy callsession control function, P-CSCF, a serving call session controlfunction, S-CSCF, an interrogating proxy session control function,I-CSCF, a media resource function controller, MRFC, or a media gatewaycontroller function, MGCF.

In some embodiments, the IMS control function is a first IMS controlfunction and the method further comprises identifying multiple instancesof a second IMS control function as being candidates for assigning tothe IMS endpoint in combination with the first IMS control function. Inthis case, the method includes obtaining a performance metric for eachcombination of candidate instances of the first and second IMS controlfunctions that is a measure of the extent to which performancerequirements for the signaling path would be met if the candidateinstances were to be assigned to the IMS endpoint in combination. Themethod also includes obtaining an emission metric for each combinationof candidate instances of the first and second IMS control functionsthat is a measure of the extent to which the candidate instances incombination would produce greenhouse gas emissions if the candidateinstances were to be assigned to the IMS endpoint in combination, giventhe energy consumption and rate of greenhouse gas emissions currentlyattributable to that combination. The consumption and rate in this caseare a combination of the respective rates currently attributable to thecandidate instances individually. The method further entailsprioritizing combinations of candidate instances of the first and secondIMS control functions relative to one another based on the performanceand emission metrics of each combination. Finally, the method involvescontrolling assignment of one of the combinations to the IMS endpoint tobe performed according to the prioritization. In one or more of theseembodiments, the first IMS control function is a serving call sessioncontrol function, S-CSCF, and the second IMS control function is eithera proxy call session control function, P-CSCF, a media resource functioncontroller, MRFC, or a media gateway controller function, MGCF.

Embodiments herein also include an assignment controller configured toperform the method(s) described above. In some embodiments, theassignment controller includes functional means or units for doing so.In one such embodiment, the assignment controller comprises one or moreprocessing circuits configured to implement those functional means orunits, e.g., as dedicated circuits or with one or more microprocessorsin conjunction with memory.

In some embodiments, the assignment controller is distributed overmultiple IMS domains.

In some embodiments, the assignment controller comprises (i) amanagement interface configured to receive a provisioning request froman IMS management system for provisioning a service for the prioritizedassignment; (ii) a session initiation protocol, SIP, interfaceconfigured to communicate with one or more serving call session controlfunctions, S-CSCFs; and (iii) a Diameter interface configured tocommunicate with a home subscriber server, HSS.

Embodiments herein also include a computer program comprisinginstructions which, when executed by at least one processor of anassignment controller, cause the assignment controller to carry out themethod(s) above. Embodiments further include a carrier containing such acomputer program, e.g., in the form of an electronic signal, an opticalsignal, a radio signal, or a computer readable storage medium.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an IP multimedia subsystem (IMS) systemthat includes an assignment controller according to one or moreembodiments.

FIG. 2 is a logic flow diagram of a method for governing the assignmentof an IMS control function instance to an IMS endpoint according to oneor more embodiments.

FIG. 3 is a logic flow diagram of a method for governing the assignmentof an IMS control function instance to an IMS endpoint in conjunctionwith the assignment of one or more other IMS control function instances,according to one or more embodiments.

FIG. 4 is a call flow diagram for assigning a P-CSCF instance in the IMSendpoint's home network during the P-CSCF discovery process and a S-CSCFinstance in the endpoint's home network during IMS registration,according to one or more embodiments.

FIG. 5 is a logic flow diagram for an assignment controller toprioritize multiple P-CSCF/S-CSCF instance combinations and to populatean HSS with one or more of the highest priority combinations, accordingto one or more embodiments.

FIG. 6 is a logic flow diagram of prioritization processing according toone or more embodiments.

FIG. 7 is a call flow diagram for assigning a virtual P-CSCF/virtualS-CSCF instance pair during an ongoing session, according to one or moreembodiments.

FIG. 8 is a block diagram of an assignment controller according to oneor more embodiments.

FIG. 9 is a block diagram of code modules for governing the assignmentof an IMS control function instance to an IMS endpoint according to oneor more embodiments.

DETAILED DESCRIPTION

FIG. 1 illustrates an IP multimedia subsystem (IMS) system 100 accordingto one or more embodiments. The system 100 may consist of one or moreIMS networks (i.e., domains) operated by one or more IMS networkoperators. As shown, an IMS endpoint 110 accesses an IMS control plane200 via an IP-connectivity access network (IP-CAN) 120. The IMS controlplane 200 enables the IMS endpoint 110 to use media services built uponInternet applications, services, and protocols that are provided byvarious application servers 300, e.g., a presence server 310, amessaging server 320, a push to talk (PTT) server 330, and a telephonyserver 340.

The IMS control plane 200 in this regard includes various functions thatcontrol the media services enabled by the application servers 300. TheIMS control plane 200 for example includes functions that register theIMS endpoint 110 with one of the IMS networks in the IMS system 100,namely the endpoint's home network. The IMS control plane 200 alsoincludes function that control the establishment, maintenance, ortearing down of sessions, such as Session Initiation Protocol (SIP)sessions. Exemplary IMS control functions in this regard include a ProxyCall Session Control Function (P-CSCF), an Interrogating Call SessionControl Function (I-CSCF), and a Serving Call Session Control Function(S-CSCF). Other IMS control functions include a media resource functioncontroller (MRFC) and a media gateway controller function (MGCF). TheIMS control plane 200 may span one or more IMS networks.

One of the IMS networks in the IMS system 100 shown deploys multipleinstances 210 ₁ . . . 210 _(A) of an IMS control function A. Where IMScontrol function A is a P-CSCF, MRFC, or MGCF, the function may belocated in the endpoint's home IMS network or in a visited IMS network.Where IMS control function A is a S-CSCF or I-CSCF, the function may belocated in the endpoint's visited IMS network. Any given instance 210 ₁. . . 210 _(A) of IMS control function A may be physical in the sensethat it is “pre-packaged” in the hardware of a dedicated physical host(i.e., server). Alternatively, any given instance 210 ₁ . . . 210 _(A)may be virtual in that it is abstracted from hardware and run assoftware on a virtual machine executed by any physical host. Some or allof the IMS control function's instances 210 ₁ . . . 210 _(A) may beco-located on the same physical host or may be geographicallydistributed throughout the IMS network that deploys function A.

Irrespective of the physical or virtual nature of the IMS controlfunction's instances 210 ₁ . . . 210 _(A), the IMS endpoint 110 isassigned one of those instances. An assignment controller 160 in thisregard governs the assignment of an IMS control function instance to theIMS endpoint 110 according to the processing 400 shown in FIG. 2.

As shown in FIG. 2, processing 400 at the assignment controller 160includes identifying multiple instances 210 ₁ . . . 210 _(A) of an IMScontrol function as being candidates for assigning to the IMS endpoint110 (Block 410). Processing 400 further involves obtaining a performancemetric for each candidate instance 210 ₁ . . . 210 _(A) (Block 420). Theperformance metric for a candidate instance 210 ₁ . . . 210 _(A) is ameasure of the extent to which performance requirements (e.g., delayrequirements) for a signaling path of an anticipated or ongoing sessionof the IMS endpoint 110 would be met if the candidate instance were tobe assigned to the IMS endpoint 110.

Processing 400 also entails obtaining an emission metric for eachcandidate instance 210 ₁ . . . 210 _(A) (Block 430). The emission metricfor a candidate instance 210 ₁ . . . 210 _(A) is a measure of the extentto which the candidate instance would produce greenhouse gas emissionsif the candidate instance were to be assigned to the IMS endpoint 110,given the energy consumption and rate of greenhouse gas emissionscurrently attributable to the candidate instance. The consumption andrate are dependent on the type of each energy source (e.g., coal,natural gas, nuclear, hydro-electric, etc.) currently being used by thecandidate instance.

Processing 400 at the assignment controller 160 further includesprioritizing the candidate instances 210 ₁ . . . 210 _(A) relative toone another based on the performance and emission metrics of eachinstance (Block 440). The assignment controller 160 in this regard morehighly prioritizes candidate instances that would yield higherperformance and lower emissions. Having prioritized the candidateinstances 210 ₁ . . . 210 _(A) in this way, processing 400 finallyinvolves controlling assignment of one of the candidate instances to theIMS endpoint 110 to be performed according to this prioritization (Block450).

By governing instance assignment in this way, the assignment controller160 in at least some embodiments advantageously reduces the overallgreenhouse gas emissions of the IMS system 100, e.g., by reducingemissions on an endpoint-by-endpoint or session-by-session basis. Thisis not something that a pure load balancing approach could accomplish.Indeed, a pure load balancing approach would just tend to equallydistribute energy consumption across physical hosts, without accountingfor the type(s) of energy source(s) (e.g., the electric grid-mix)implicated in doing so. As compared to a pure load balancing approach,then, the assignment controller 160 in at least some embodiments tendsto preferentially load physical hosts that are currently usingemission-light energy sources (e.g., wind, hydroelectricity, andnuclear), as distinguished from emission-heavy energy sources (e.g.,coal and natural gas). The assignment controller 160 of course balancesthis preference for loading emission-light physical hosts againstmeeting performance requirements.

In at least some embodiments, the emission metric for a candidateinstance is real-time in the sense that it is based on the actual orestimated amount of energy that the instance is consuming and the actualor estimated rate at which the instance is producing emissions when theassignment controller 160 is performing the prioritization. Similarly,the performance metric in some embodiments is real-time in the sensethat it is based on the actual or estimated degree to which thecandidate instance is currently able (e.g., in terms of availableprocessing resources) to meet signaling path performance requirements.Of course, the real-time nature of the performance metric and/oremission metric may nonetheless be qualified by practical constraints onhow often the metrics can and/or need to be updated at the assignmentcontroller 160. In one or more embodiments, therefore, an instance'sperformance metric and/or emission metric are deemed “current” accordingto a defined time resolution at which the assignment controller 160dynamically updates the metric(s). In one embodiment, for example, theassignment controller 160 updates the performance metric and/or emissionmetric for a candidate instance occasionally or periodically accordingto a defined time resolution (e.g., every hour). In at least someembodiments, this means that the processing 400 in FIG. 2 is performedperiodically or occasionally using performance metrics and/or emissionmetrics that have been updated since a previous time that the method wasperformed.

In one or more embodiments, the assignment controller 160 obtains theperformance metrics and/or emission metrics for one or more of thecandidate instances 210 ₁ . . . 210 _(A) by receiving those metrics fromanother node, such as an IMS management system 150.

Alternatively or additionally, the assignment controller 160 obtains theperformance metrics and/or emission metrics for one or more of thecandidate instances 210 ₁ . . . 210 _(A) by calculating or otherwisedetermining (e.g., with a look-up table) those metrics itself.

In one embodiment, for example, the assignment controller 160 determinesa number of parameters including (i) the amount of energy that acandidate instance is currently consuming from each of one or more typesof energy sources; and (ii) the rate at which those types of energysources are currently emitting greenhouse gases. In some embodiments,the assignment controller 160 determines these parameters by receivingone or more of them from another node, such as the IMS management system150. Regardless, the assignment controller 160 then uses thoseparameters to calculate the emission metric for the candidate instanceas being the total amount of emissions that the instance would produceif the instance were to be immediately assigned to the IMS endpoint 110for an assumed duration (e.g., the next hour). The controller 160 mayfor instance determine what additional real-time energy the candidateinstance would have to consume (above and beyond the instance's currentenergy consumption) if it were to be assigned to the IMS endpoint 110,and then use the determined energy consumption amount(s) and emissionrate(s) to calculate the total emissions that would result over thecourse of the assumed duration. The total amount of greenhouse gasemissions in this regard may be specified in any appropriate units. Inembodiments where the total emissions are specified in kilograms ofcarbon dioxide equivalency, Kg CO₂e, the assignment controller 160 maycalculate the total emissions produced by a particular candidateinstance as:

$\begin{matrix}{{{CO}_{2}e_{TOTAL}} = {\sum\limits_{i}{{P_{i}( {t,{\Delta\; t}} )} \cdot {R_{i}( {t,{\Delta\; t}} )}}}} & (1.1)\end{matrix}$

for each of i types of energy sources used by the instance, whereP_(t)(t,Δt) is the estimated or measured amount of energy in Kilowatthours (KWh) that the instance will consume from energy source type iduring an assumed duration Δt (e.g., 1 hour) starting from time t, andR_(t)(t,Δt) is the estimated rate (in Kg CO₂e per KWh) at which theinstance will produce greenhouse gas emissions when consuming energyfrom energy source type i during the assumed duration Δt starting fromtime t. The estimated or measured amount of energy consumed P_(t)(t,Δt)by a particular candidate instance may be the entire amount of energyconsumed by the instance's physical host if the host only executes thatone instance, or may be only a portion of the energy consumed by theinstance's physical host if the host executes more than one instanceand/or more than one IMS control function. Exemplary emission ratesR_(t)(t,Δt) for different types of energy sources include 0.012 Kg CO₂eper KWh for wind-based energy sources, 0.013 Kg CO₂e per KWh forhydroelectricity-based energy sources, 0.014 Kg CO₂e per KWh fornuclear-based energy sources, 0.693 Kg CO₂e per KWh fornatural-gas-based energy sources, and 1.150 Kg CO₂e per KWh forcoal-based energy sources.

Note, though, that the performance metrics, emission metrics, energyconsumption, and/or emission rate may be specified in any form or unitsthat directly or indirectly indicate their respective measures. Ratherthan being directly specified in terms of Kg CO₂e per KWh, for example,an emission rate may be specified in terms of an index that is mapped toa particular Kg CO₂e per KWh value or range of values. Furthermore, allinstances deployed on hosts at the same data center may be deemed tohave the same emission rate, based on the assumption that all hosts usethe same energy sources. Alternatively, the emission rate may bespecified on a host-by-host basis to allow different hosts within thesame data center to use different energy source mixes.

Regardless, in some embodiments, the assignment controller 160determines the rate of greenhouse gas emissions currently attributableto a candidate instance directly as a function of the time of day, e.g.,with the instance associated with different emission rates at differenttimes of day, depending on the different type(s) of energy source(s)used at different times of day. In other embodiments, though, theassignment controller 160 determines the rate of greenhouse gasemissions currently attributable to a candidate instance directly as afunction of one or more other parameters. In general, then, theassignment controller 160 makes this determination in accordance with adefined policy. The policy effectively defines possible ratesattributable to the candidate instance depending on certain conditions.The policy specifies these conditions in terms of (i) different times ofday; (ii) different locations of the hardware executing the instance;(iii) different types of one or more energy sources used by theinstance; (iv) different types of media for the session (e.g., video vs.only audio); and/or (v) different durations of the session. Depending onwhat services are subscribed to, a different policy may apply (e.g., asto what video coder a subscriber may be allowed to use that requiresless resources at certain times of the day).

Accordingly, in certain embodiments, the location of the hardwareexecuting a candidate instance affects both the emission metric and theperformance metric for that instance. In particular, the location of thephysical host executing the instance affects the emission metric, atleast indirectly, because different locations are inherently tied todifferent types of energy sources. And the location of the physical hostexecuting the instance affects the performance metric because differentlocations are positioned at different distances from the IMS endpoint110 and are thereby associated with different signaling latencies. Inone or more embodiments, therefore, the performance metric for acandidate instance is, at least in part, a measure of the extent towhich signaling delay requirements for the signaling path would be metif the candidate instance were to be assigned to the IMS endpoint 110.These delay requirements are dependent on a location of the instancerelative to the current location of the IMS endpoint 110. In these andother embodiments, therefore, the assignment of an instance to an IMSendpoint 110 is particularized for that particular endpoint 110 becauseit accounts for the location of that particular endpoint 110.

As one simple example in this regard, the assignment controller 160 mayprioritize a first candidate instance above a second candidate instanceif the first instance produces less greenhouse gas emissions than thesecond instance. The controller 160 may do so even if the firstcandidate instance cannot meet the signaling path's delay requirementsas well as the second candidate instance (due to for instance the firstinstance not being as physically close to the IMS endpoint 110), e.g.,as long as the first candidate instance can come within at least acertain threshold (e.g., 0.5 ms) of those requirements.

In one or more other embodiments, the assignment controller 160prioritizes the candidate instances also based on historical dataindicating which of the candidate instances have actually been assignedto the same or a different IMS endpoint 110 in the past. If, forexample, the same candidate instance has historically been assigned to aparticular IMS endpoint 110 between the hours of 9 PM and 3 AM, thatcandidate instance may be prioritized higher between those hours. Thisscenario may occur in practice if for instance the IMS endpoint 110remains stationary at a fixed location between 9 PM and 3 AM, suggestingthat the historically chosen candidate instance's performance andemission metrics will likely continue to have their historical valuesbetween 9 PM and 3 AM for that endpoint 110 (assuming that the candidateinstance continues to be executed by hardware at the same location).This is the case in light of the metrics' dependency on the locations ofthe candidate instance's hardware and the IMS endpoint 110.

In at least some embodiments, the IMS system 100 monetizesemission-prioritized assignment of candidate instances by offering it asa service that an IMS endpoint 110 must pay for, i.e., “green-IMS as aservice”. In one embodiment, for example, the assignment controller 160obtains a billing parameter that indicates whether the IMS endpoint 110is subscribed to a service providing emission-prioritized assignment ofcandidate instances. The controller 160 then determines whether toperform the processing 400 in FIG. 2 based on the billing parameter.That is, the controller 160 determines to perform processing 400 if theIMS endpoint 110 has subscribed to and/or paid for the prioritizationservice.

Alternatively or additionally, the billing parameter indicates to whatextent the IMS endpoint 110 is subscribed to the prioritization service.For example, different subscription levels (e.g., bronze, silver, gold)to the service provide different levels of prioritization, with highersubscription levels entitling an IMS endpoint 110 to prioritization thatproduces lower emissions. The differentiation may be realized throughdifferent prioritization algorithms that prioritize candidate instancesfor lower emissions to different extents and/or through conflictresolution algorithms that prioritize higher subscriptions above lowersubscriptions when the subscriptions are competing for the same instanceof the IMS control function.

Irrespective of how the candidate instances are prioritized, though, theassignment controller 160 in at least some embodiments performs step 450in FIG. 2 by manipulating endpoint-specific configuration data thatgoverns the assignment so that the configuration data reflects theprioritization. In doing so, the assignment controller 160 influencesthe way that some other node uses the configuration data to actuallyassign an instance to the specific IMS endpoint 110.

In one embodiment, for example, the controller 160 manipulatesendpoint-specific configuration data that is maintained by a homesubscriber server (HSS) 240 shown in FIG. 1. The configuration data inthis case may be included in the HSS record for a particular IMSendpoint 110, where that HSS record contains endpoint-specific dataneeded by the IMS system 100 to deliver services to the endpoint 110.

Consider a simple example where the controller 160 controls assignmentof an S-CSCF instance to the IMS endpoint 110 (i.e., IMS controlfunction A is an S-CSCF). In this case, the HSS 240 stores a list of oneor more S-CSCF instances that are candidates for assigning to thespecific IMS endpoint 110. The controller 160 prioritizes this list ofone or more one or more candidate instances using the processing 400 inFIG. 2 to account for greenhouse gas emissions. The controller 160 mayfor instance provide the HSS 240 with tags of priority in a list ofS-CSCF instances, so as to populate the list for the HSS 240. In someembodiments, the controller 160 does so before the registration processduring which the IMS endpoint 110 registers with one of the IMS networksin the IMS system 100, namely its home IMS network. This way, when thehome I-CSCF assigns the IMS endpoint 110 an S-CSCF instance during theregistration process based on the list of one or more one or more S-CSCFcandidate instances in the HSS, the list will have already beenprioritized to account for greenhouse gas emissions. In otherembodiments, by contrast, the controller 160 manipulatesendpoint-specific configuration data that is maintained by a domain nameserver (DNS) 130 and/or a dynamic host configuration protocol (DHCP)server 140 as shown in FIG. 1. The configuration data in this case maybe included in the DNS and/or DHCP record for a particular IMS endpoint110, where that record contains endpoint-specific data needed by the DNSand/or DHCP server for returning a fully qualified domain name (FQDN)and/or IP address to the endpoint 110.

Consider an example where the controller 160 controls assignment of anP-CSCF instance to the IMS endpoint 110 during a P-CSCF discoveryprocess that occurs prior to the IMS endpoint 110 registering with oneof the IMS networks in the IMS system 100. During the discovery process,the endpoint 110 attempts to discover a P-CSCF in one of the IMSnetworks in the IMS system 100, be it a visited network or theendpoint's home network. The IMS endpoint 110 in some embodiments doesso by querying the DNS 130 and/or the DHCP server 140. The endpoint 110may for instance query the DHCP server 140 for an IP address of a P-CSCFinstance, where the DHCP server 140 dynamically allocates IP addresseson the fly to new P-CSCF instances without the need for FQDNs.Alternatively, the endpoint 110 may determine (e.g., be pre-configuredwith) the FQDN of a P-CSCF instance and query the DNS 130 to resolvethat FQDN into an IP address of a P-CSCF instance. With this in mind,the controller 160 in some embodiments prioritizes the P-CSCF candidateinstances for the IMS endpoint 110 before or in conjunction with theendpoint engaging in P-CSCF discovery. The controller 160 in doing somanipulates endpoint-specific configuration data at the DNS 130 and/orDHCP server 140 to reflect this prioritization. The controller 160 mayfor instance prioritize a list of one or more IP addresses maintained atthe DHCP server 140 and/or at the DNS 130. This way, when the IMSendpoint 110 queries the DNS 130 and/or the DHCP server 140, the IPaddress of a P-CSCF instance with higher priority (e.g., lowergreenhouse gas emissions) will be returned to the endpoint 110.Alternatively, all or part of the prioritized list of P-CSCF IPaddresses will be returned to the IMS endpoint 110, which then attemptsto use the P-CSCF instances in priority order.

Of course, while the above example discussed manipulating configurationdata at the DNS 130 and/or DHCP server 140 for P-CSCF assignment, thecontroller 160 may alternatively or additionally manipulateconfiguration data at the HSS 240 or any other node (e.g., a policyserver or gateway node outside of the IMS) for such purposes too. Forexample, configuration data at the HSS 240 may govern instanceassignment for any type of IMS control function, be it the P-CSCF,S-CSCF, I-CSCF, MRFC, MGCF, etc. Broadly, therefore, any node and/orprocedure may be used for instance assignment according to embodimentsherein, as long as the assignment controller 160 directly or indirectlycontrols that node and/or procedure such that instance assignment occursaccording the controller's emission-aware prioritization.

As these examples demonstrate, the assignment controller 160 in at leastsome embodiments performs all or some of the processing 400 in FIG. 2 inanticipation (i.e., in advance) of the IMS endpoint 110 engaging in asession. As part of this anticipation, the controller 160 may performall or some of the processing 400 before the IMS endpoint 110 evenestablishes IP connectivity and/or registers with an IMS network in theIMS system 100. And, as shown as an option in FIG. 2, the processing 400may be iterative in the sense that the controller 160 performs thatprocessing 400 periodically (e.g., hourly) or occasionally “in thebackground”, as part of this anticipation. This way, when the instanceassignment eventually occurs (e.g., as part of establishing IPconnectivity and/or as part of IMS registration), the controller 160ensures that the assignment will be performed based on up-to-dateperformance and/or emission metrics. In embodiments where an IMSendpoint 110 subscribes to a service providing emission-basedprioritization, for example, the controller 160 performs processing 400periodically (e.g., every hour) from the time when the IMS endpoint 110subscribes to the service. The IMS endpoint 110 in this case does noteven have to be powered on or connected to the IMS system 100 in orderfor the assignment controller 160 to prepare prioritized instanceassignment for the endpoint 110.

In one or more of these embodiments where the controller 160 performsprocessing 400 in anticipation of a session, the controller 160 controlswhich instance is assigned to the IMS endpoint 110 at IP connectivityestablishment or IMS registration, and that same assignment remainseffective for the duration of the IP connectivity or registration,respectively. In one embodiment where the controller 160 controls theassignment of an S-CSCF instance upon the endpoint 110 registering orre-registering with an IMS network, for example, that same S-CSCFinstance remains assigned to the endpoint 110 for the duration of anygiven registration.

In other embodiments, the controller 160 controls instance assignment insuch a way that it can be performed at any time, even during an ongoingsession. These embodiments prove particularly applicable when two ormore of the candidate instances are virtual instances in a virtualizedIMS system 100. Indeed, because a virtual instance is abstracted fromthe hardware of any particular physical host, the virtual instance isable to be migrated from one host to another while still preservingservice continuity. In one or more embodiments, therefore, theassignment controller 160 controls instance assignment by directing thatthe instance assigned to the IMS endpoint be changed from an old virtualinstance to a new virtual instance and that the state of the old virtualinstance be migrated to a state of the new virtual instance. Theassignment controller 160 in at least some embodiments does do byrequesting or otherwise triggering the IMS management system 150 toperform the assignment (i.e., migration) according to the controller'sprioritization of the candidate instances. This may involve thecontroller 160 for example identifying the new virtual instance to beassigned to the IMS endpoint 110 as being the highest priority instanceand requesting that the IMS management system 150 migrate the state ofthe virtual instance currently assigned to the endpoint 110 to the newvirtual instance. Alternatively, the controller 160 may send the IMSmanagement system 150 a prioritized list of one or more virtualcandidate instances and requests that the IMS management system 150itself select a new virtual instance for the IMS endpoint 110 based onthat list. Upon selecting the new virtual instance, the IMS managementsystem 150 migrates the state of the virtual instance currently assignedto the endpoint 110 to the new virtual instance.

Although the above embodiments have focused on assigning an instance 210₁ . . . 210 _(A) of a single IMS control function A to an IMS endpoint110, such may actually be performed in conjunction with assigning aninstance of one or more other IMS control functions to the endpoint 110.For example, the controller 160 in some embodiments prioritizescandidate instances 210 ₁ . . . 210 _(A) for IMS control function A incombination with prioritizing candidate instances 220 ₁ . . . 220 _(B)for another IMS control function B. IMS control function B in thisregard may be in the same or a different IMS network than IMS controlfunction A. IMS control function B may be for instance a home orvisiting P-CSCF, whereas IMS control function A is a home S-CSCF. In anyevent, prioritizing candidate instances of multiple IMS controlfunctions in combination may proceed similarly to any of the aboveembodiments related to prioritizing candidate instances of a single IMScontrol function, but be based on the combination of multiple IMScontrol functions rather than on an individual IMS control function.FIG. 3 illustrates processing 500 performed by the assignment controller160 in one or more of these embodiments.

As shown in FIG. 3, processing 500 at the assignment controller 160includes not only identifying multiple instances 210 ₁ . . . 210 _(A) ofa first IMS control function (e.g., control function A 210) as beingcandidates for assigning to the IMS endpoint 110 (Block 510), but alsoidentifying multiple instances 220 ₁ . . . 220 _(B) of a second IMScontrol function (e.g., control function B 220) as being candidates forassigning to the IMS endpoint 110 (Block 520) in combination. Processing500 further includes obtaining a performance metric for each combinationof candidate instances of the first and second IMS control functions(Block 530). A performance metric for a combination of candidateinstances in this regard is a measure of the extent to which performancerequirements for the signaling path would be met if the candidateinstances were to be assigned to the IMS endpoint 110 in combination.The assignment controller 160 may itself determine such a performancemetric by combining performance metrics for each individual candidateinstance in the combination. For example, if the performance metriccharacterizes latency, the performance metric may be added as a pathbudget for the session establishment. Similarly, processing 500 alsoincludes obtaining an emission metric for each combination of candidateinstances of the first and second IMS control functions (Block 540). Anemission metric for a combination of candidate instances is a measure ofthe extent to which the candidate instances in combination would producegreenhouse gas emissions if the candidate instances were to be assignedto the IMS endpoint in combination, given the energy consumption andrate of greenhouse gas emissions currently attributable to thatcombination. This energy consumption and emission rate are a combinationof the respective rates currently attributable to the candidateinstances individually. Processing 500 further entails prioritizingcombinations of candidate instances of the first and second IMS controlfunctions relative to one another based on the performance and emissionmetrics of each combination (Block 550). Such prioritization involvesmore highly prioritizing (i.e., ranking) combinations that would yieldhigher performance and lower emissions. Finally, processing 500 includescontrolling assignment of one of the combinations to the IMS endpoint110 to be performed according to the prioritization (Block 560).

The controller 160 in some embodiments controls assignment of one of thecombinations to the IMS endpoint 110 by manipulating endpoint-specificconfiguration data maintained by a single node (e.g., the HSS 240). Thecontroller 160 may for instance prioritize a list of one or morecombinations maintained by the single node. In other embodiments,though, the controller 160 manipulates endpoint-specific configurationdata maintained by different nodes (e.g., both the HSS 240 and the DNS130, the DHCP Server 140, or a policy server such as a Policy andCharging Rules Function, PCRF). For example, the controller 160 maymanipulate data maintained by one node (e.g., the DNS 130, DHCP Server140, or a policy server) to control which candidate instance 210 ₁ . . .210 _(A) of Control Function A (e.g., P-CSCF) is assigned to theendpoint 110, but manipulate data maintained by a different node (e.g.,HSS 240) to control which candidate instance 220 ₁ . . . 220 _(B) ofControl Function B (e.g., S-CSCF) is assigned to the endpoint 110.

As a simple example of this, the controller 160 may control assignmentof P-CSCF/S-CSCF instance combinations (i.e., pairs) to the endpoint110. To do so, the controller 160 may manipulate a list of one or moreP-CSCF/S-CSCF instance combinations maintained by the HSS 240 to reflectthe controller's emission-aware prioritization of those combinations.Alternatively, the controller 160 may manipulate a list of one or moreP-CSCF instances maintained by the DNS 130 or DHCP Server 140, or apolicy server, in conjunction with manipulating a list of one or moreS-CSCF instances maintained by the HSS 240 so that those two separatelists collectively reflect the controller's emission-awareprioritization of P-CSCF/S-CSCF instance combinations.

FIG. 4 illustrates additional details of this example according to oneor more “non-roaming” embodiments where the IMS endpoint 110 is assigneda P-CSCF instance in the endpoint's home network during the P-CSCFdiscovery process and is assigned a S-CSCF instance in the endpoint'shome network during IMS registration. Moreover, in the one or moreembodiments illustrated by FIG. 4, the assignment controller 160performs the processing in FIG. 3 before P-CSCF discovery and IMSregistration, in anticipation of the endpoint 110 engaging in the P-CSCFdiscovery process, IMS registration, and, eventually, a session (aseither the originating or terminating endpoint).

As shown in FIG. 4, the IMS management system 150 optionally provisionsthe assignment controller 160 with information to govern emission-awareP-CSCF/S-CSCF assignment (Step 605). This information may include theperformance metrics and/or the emission metrics that the controller 160employs to prioritize P-CSCF/S-CSCF instance combinations for theendpoint 110, or may include any data, parameters, and/or policies usedby the controller 160 to determine some or all of those metrics. Theprovisioning information may further include a billing parameter thatindicates whether and/or to what extent the IMS endpoint 110 issubscribed to a service providing emission-aware, prioritizedP-CSCF/S-CSCF assignment.

Meanwhile, an I-CSCF 250 in the IMS endpoint's home network may overseasthe overall network (e.g., there may be only one I-CSCF instance in thehome network). This I-CSCF 250 identifies different possiblecombinations of home P-CSCF/S-CSCF instances (Step 610). The I-CSCF 250handshakes with the HSS 240 in the endpoint's home network to providethe HSS 240 with the identified combinations (Step 615). And finally theassignment controller 160 handshakes with the HSS 240 to itself retrievethe identified combinations (Step 620). This identification andhandshaking in some embodiments occurs periodically or occasionally inanticipation of the endpoint 110 engaging in the P-CSCF discoveryprocess, IMS registration, and, eventually, a session. This ensures thatthe HSS 240 and assignment controller 160 will have up-to-dateinformation about the different possible combinations of homeP-CSCF/S-CSCF instances in the home network when prioritization andP-CSCF and S-CSCF instance assignment occurs.

Having identified the different possible P-CSCF/S-CSCF combinations byretrieving them from the HSS 240, the assignment controller 160prioritizes those combinations relative to one another based on theperformance metric and emission metric for each combination, asdescribed with respect to FIG. 3 (Step 625). The assignment controller160 then controls P-CSCF/S-CSCF assignment that will eventually occurduring the P-CSCF discovery process and IMS registration by manipulatingend-point specific data that governs that assignment to reflect itsprioritization (Step 630). As shown in FIG. 4, this may entail justmanipulating a list of one or more P-CSCF/S-CSCF instance combinationsmaintained by the HSS 240 to reflect the controller's emission-awareprioritization of those combinations. Alternatively, the controller 160may manipulate a list of one or more P-CSCF instances maintained by theDNS 130 or DHCP Server 140 or a policy server (not shown) in conjunctionwith manipulating a list of one or more S-CSCF instances maintained bythe HSS 240 so that those two separate lists collectively reflect thecontroller's emission-aware prioritization of P-CSCF/S-CSCF instancecombinations.

With emission-aware prioritization of P-CSCF/S-CSCF instancecombinations indicated in the HSS 240 and/or DNS/DHCP 130/140, and/or apolicy server, P-CSCF/S-CSCF assignment to the IMS endpoint 110 willaccount for that prioritization when assignment eventually occurs.Indeed, when the IMS endpoint 110 later engages in a P-CSCF discoveryprocess, as shown, the already prioritized P-CSCF instance list at theHSS 240, the DNS/DHCP 130/140, or a policy server (not shown) willgovern P-CSCF instance assignment (Step 635). In some embodiments, forexample, all or part of the prioritized P-CSCF instance list may beprovided to the IMS endpoint 110 by the DNS 130/DHCP 140 or by the HSS240, e.g., indirectly via an interface, policy server, gateway, etc.,whereupon the IMS endpoint 110 attempts to use the P-CSCF instances inpriority order. The HSS 240 or the DNS/DHCP 130/140 in this regard maynot actually know that the P-CSCF instance list is prioritized toaccount for greenhouse gas emissions. Similarly, when the IMS endpoint110 thereafter engages in an IMS registration process, the I-CSCF 250interrogates the HSS for the prioritized S-CSCF instance list (Step 645)in response to receiving an IMS registration message from the endpoint110 (Step 640). Having obtained this prioritized S-CSCF instance list(Step 640), the I-CSCF then selects the S-CSCF instance to assign to theendpoint 110 in accordance with that list. Again, the I-CSCF may notactually know that the S-CSCF instance list is prioritized to accountfor greenhouse gas emissions. In at least some embodiments, once theS-CSCF assignment procedure is performed, the I-CSCF 250 sends to thechosen S-CSCF, the following data string: P-CSCF address/name, PublicUser Identity, Private User Identity, P-CSCF network identifier, and theIP address of the endpoint 110.

In at least some embodiments, the I-CSCF 250 reports the S-CSCF instanceassigned to the IMS endpoint 110 to the HSS 240 (Step 655). And if theDNS/DHCP 130/140 assigned the P-CSCF instance, the P-CSCF instanceassigned may also be reported back to the HSS 240. The HSS 240 thenreports the P-CSCF/S-CSCF instance combination actually assigned to theendpoint 110 to the assignment controller 160 (Step 660), in order tobuild a history of actual assignments that can be used to improveemission-aware prioritization. Moreover, in one or more embodiments, theassignment controller 160 also handshakes with the IMS management system150 for provisioning information updates (Step 670). These updates mayinclude for instance updated performance and/or emission metrics,updated data, parameters, and/or policies used to determine suchmetrics, or updated S-CSCF/P-CSCF instance combinations that have feweremissions. The IMS management system 150 may for example dynamicallyadjusts its sets of policies, data, emission metrics, parameters, andthe like as a function of time-of-the-day, day-of-the-week, etc. for thepurpose of reducing emissions. Demographics, seasons, demands on thecloud, etc. may change and result in prioritization changes. Accountingfor this, control from the IMS management system 150 is dynamic innature and adjusts to these requirements.

In one or more embodiments, the approach described in FIG. 4 provesadvantageous in that it is non-intrusive and does not requiremodification to the existing message sequence dictated by current IMSstandards (e.g., IMS SIP signaling) as described in TS 23-228 Release12. For example, as described in clause 5.1.1.0 of TS 23-228 Release 12,when the IMS endpoint 110 is aware of more than one P-CSCF address, theP-CSCF instance selection shall be based on home operator configuredpolicy. This policy is specified herein as the endpoint-specific datawhich the HSS 240 manages and which the assignment controller 240manipulates to account for greenhouse gas emissions. Similarly, clause5.1.2.1 of TST 23-228 Release 12 states that when an IMS endpoint 110attaches and makes itself available for access to IMS services byexplicitly registering in the IMS, a S-CSCF instance shall be assignedto serve the IMS endpoint 110. The same clause describes that theassignment of an S-CSCF instance is performed in the I-CSCF 250. Someinformation is needed in the selection of the S-CSCF instance, includingrequired capabilities for user services (provided by the HSS 240) andoperator preferences on a per-user basis (e.g., a predefined S-CSCFinstance priority that the assignment controller 160 sets in the HSS240). Once the S-CSCF instance assignment is completed, the I-CSCF sendsto the chosen S-CSCF instance, the following data string: P-CSCFaddress/name, Public User Identity, Private User Identity, P-CSCFnetwork identifier, IMS endpoint IP address to the selected S-CSCFinstance.

Although FIG. 4 illustrated “non-roaming” embodiments where the IMSendpoint 110 is assigned P-CSCF and I-CSCF instances in its home IMSnetwork, the embodiments are readily extendable to “roaming” embodimentswherein the IMS endpoint 110 is assigned a P-CSCF instance in a visitedIMS network and assigned an S-CSCF instance in its home IMS network. Inat least some of these “roaming” embodiments, different IMS networksimplement different instances of the assignment controller 160 and sendinter-domain control signaling between themselves to coordinateemission-aware assignment of the visited P-CSCF instance and home S-CSCFinstance. Moreover, those skilled in the art will appreciate that FIG. 4embodiments apply equally to intra-domain or inter-domain sessions, aswell as to originating or terminating sessions, of the IMS endpoint 110.

For example, the assignment controller 160, in anticipation of the IMSendpoint 110 terminating a session, may proactively handshake with anS-CSCF instance in a “potentially originating” IMS network. The networkis potentially originating in the sense that it may at some point in thefuture originate a session towards the IMS endpoint 110, but has not yetdone so. As part of this handshake process, the assignment controller160 queries the potentially originating S-CSCF instance for the identityof the I-CSCF instance and therefore HSS in the endpoint's home networkthat the S-CSCF instance would target for connecting to the IMS endpoint110, were it to originate a session towards the endpoint 110. Indeed,the potentially originating S-CSCF instance knows from the localapplication server (AS) what I-CSCF instance in the endpoint'sterminating network to use, were it to originate a session towards thatendpoint 110. The assignment controller 160 may for example retrieve theidentity of I-CSCF and/or the identity of HSS. Correspondingly, theassignment controller 160 handshakes with HSS 240 for different possibleP-CSCF/S-CSCF instance combinations as described above to provision theendpoint's HSS 240 for emission-aware assignment. The controller 160then prioritizes those combinations and manipulates endpoint-specificdata managed by the HSS 240 to reflect that prioritization.

Although in some embodiments the HSS 240 maintains a list of multipleP-CSCF/S-CSCF instance combinations and the controller 160 prioritizesthat list, in other embodiments the controller 160 prioritizes multipleP-CSCF/S-CSCF instance combinations but only populates the HSS 240 withone or more of the highest priority combinations. FIG. 5 illustratesexemplary processing 800 for these latter embodiments in the context ofscenarios that involve provisioning from the IMS management system 150and an inter-domain session.

As shown in FIG. 5, processing 800 at the controller 160 in someembodiments includes receiving provisioning information from the IMSmanagement system, e.g., as described above with respect to FIG. 3(Block 810). In at least some embodiment, this information describesrequirements of an anticipated session in terms of service options(e.g., packet delivery rate or delay requirements). The information mayalternatively or additionally describe policies for determiningperformance and/or emission metrics (e.g., if video, then use broadbandconnection). Still further, the information may describe billingparameters (e.g., whether the IMS endpoint 110 has subscribed to theemission-aware prioritization service so that the endpoint 110 can bebilled accordingly). Regardless, processing 800 further entailsinitiating discovery of the application server in the terminatingnetwork that has media requirements (e.g., bandwidth, latency, availableendpoint coding resources, etc.) for a session that the IMS endpoint 110is anticipated to terminate (Block 820). Processing 800 next involvesdetermining whether the HSS 240 in the terminating network has providedthe controller 160 with new prioritized P-CSCF/S-CSCF pairs since aprevious update period (Block 830). If not, the controller 160 revertsto a default session setup (Block 840). If so, though, the controllerruns its prioritization process with respect to possible P-CSCF/S-CSCFpairs, including the new ones just identified (Block 850). Thisprioritization process returns one or more P-CSCF/S-CSCF pairs,whereupon the controller 160 handshakes with the HSS 240 to populate theHSS 240 with those resulting pairs (Block 860).

In more detail, FIG. 6 illustrates the prioritization process accordingto at least some embodiments. The process 900 includes inputting allavailable P-CSCF/S-CSCF pairs into the local memory of the assignmentcontroller 160 for analysis (Block 910). The process 900 then entailsgiving each pair a priority based on the performance metric and emissionmetric for that pair (Block 920). In one embodiment, this involves firstcoarsely prioritizing the pairs based on the pairs' respective powerconsumption (e.g., available as an HSS record), and then more finelyprioritizing the pairs based on the pairs' respective rate of greenhousegas emissions (e.g., as determined based on one or more policiesprovisioned by the IMS management system 150, such as a mapping oftime-of-day to emissions or energy sources). In this case, the nowfinely prioritized pairs are then checked for compliance with theperformance requirements of the anticipated session (e.g., as specifiedby service options provisioned by the IMS management system 150). If theprioritized pairs meet these performance requirements, the process 900returns one or more pairs with the highest priority (Block 930).

FIG. 7 illustrates additional details of some embodiments where the IMSendpoint 110 is assigned a virtual P-CSCF/virtual S-CSCF instance pairduring an ongoing session. As shown, the assignment controller 160prioritizes different virtual P-CSCF/virtual S-CSCF instance pairs (Step1025) even while the IMS endpoint 110 is engaged in an ongoing session(Step 1030). If the prioritization reveals that the virtualP-CSCF/virtual S-CSCF instance pair 270 currently being used for theongoing session is no longer the highest priority pair, the assignmentcontroller 160 requests the IMS management system 150 to assign a newvirtual P-CSCF/virtual S-CSCF instance pair 280 to the IMS endpoint 110that has a higher priority (Step 1035). In particular, the controller160 in some embodiments identifies the new virtual P-CSCF/virtual S-CSCFinstance pair 280 as being the highest priority pair and requests thatthe IMS management system 150 migrate the state of the pair 270currently assigned to the endpoint 110 to the new pair 280. Afterperforming this migration process (Step 1040), the IMS endpoint 110continues the ongoing session using the new pair 280 (Step 1045), whilemaintaining service continuity.

Although FIGS. 4-7 were described with combinations of P-CSCF/S-CSCFinstances, the illustrated embodiments are equally applicable to anytype and any number of IMS control function instances. Indeed, as yetanother example, other embodiments herein control assignment of anS-CSCF instance in combination with a I-CSCF instance, MRFC instance,and/or MGCF instance. Moreover, although mostly exemplified above withboth a home P-CSCF and a home S-CSCF, the endpoint 110 in otherembodiments may be assigned a visited P-CSCF in combination with a homeS-CSCF.

Note that the above embodiments do not require that an IMS controlfunction instance be dedicated to a single IMS endpoint 110. In fact, inat least some embodiments, the assignment controller 160 may assign morethan one IMS endpoint to the same (i.e., shared) IMS control functioninstance. Moreover, the above embodiments do not require that an IMSendpoint 110 be associated with a single user. In one or moreembodiments, for example, an IMS endpoint 110 is associated with atenant operator of a virtualized IMS network deployed on the hardware ofanother IMS network's operator (i.e., a tenant who is providedIMS-as-a-service in a multi-tenant approach).

With the above modifications and variations in mind, FIG. 8 illustratesadditional details of the assignment controller 160 according to one ormore embodiments. The assignment controller 160 is configured, e.g., viafunctional means or units 1130-1160, to implement processing 400 forgoverning the assignment of an IMS control function instance to an IMSendpoint 110. The assignment controller 160 in some embodiments forexample includes an identifying means or unit 1130 configured toidentify multiple instances 210 ₁ . . . 210 _(A) of an IMS controlfunction as being candidates for assigning to the IMS endpoint 110. Theassignment controller 160 in such a case further includes an obtainingmeans or unit 1140 configured to obtain a performance metric and anemission metric for each candidate instance 210 ₁ . . . 210 _(A), asdescribed above with respect to FIG. 2. The controller 160 also includesa prioritizing means or unit 1150 configured to prioritize the candidateinstances 210 ₁ . . . 210 _(A) relative to one another based on theperformance and emission metrics of each instance. The assignmentcontroller 160 in this regard more highly prioritizes candidateinstances that would yield higher performance and lower emissions.Having prioritized the candidate instances 210 ₁ . . . 210 _(A) in thisway, the controller 160 finally includes a controlling means or unit1160 configured to control assignment of one of the candidate instancesto the IMS endpoint 110 to be performed according to thisprioritization.

In at least some embodiments, the assignment controller 160 comprisesone or more processing circuits 1110 configured to implement processing400, such as by implementing functional means or units 1130-1160. In oneembodiment, for example, the controller's processing circuit(s) 1110implement functional means or units 1130-1160 as respective circuits.The circuits in this regard may comprise circuits dedicated toperforming certain functional processing and/or one or moremicroprocessors in conjunction with memory 1120. In embodiments thatemploy memory 1120, which may comprise one or several types of memorysuch as read-only memory (ROM), random-access memory, cache memory,flash memory devices, optical storage devices, etc., the memory storesprogram code that, when executed by the one or more for carrying out oneor more microprocessors, carries out the techniques described herein.

In one or more embodiments, the assignment controller 160 also comprisesone or more communication interfaces 1100. The one or more communicationinterfaces 1100 include various components (not shown) for sending andreceiving data and control signals. More particularly, the interface(s)1100 include a transmitter that is configured to use known signalprocessing techniques, typically according to one or more standards, andis configured to condition a signal for transmission (e.g., over the airvia one or more antennas). Similarly, the interface(s) 1100 include areceiver that is configured to convert signals received (e.g., via theantenna(s)) into digital samples for processing by the one or moreprocessing circuits 1110. For example, the controller 160 may include amanagement interface to receive provisioning information from and torelay back updates to the IMS management system 150, a SIP interface tohandshake with or read from a S-CSCF, and/or a Diameter interface tohandshake with, read from, or write to an HSS.

Note that the assignment controller 160 in some embodiments is deployedon a single physical host. In other embodiments, though, the assignmentcontroller 160 is distributed over multiple physical hosts, e.g., ingeographically distributed IMS networks, such that the one or moreprocessing circuits 1140 are those of the distributed hosts. In thiscase, the distributed instances of the assignment controller 160 maycommunicate with one another to realize the techniques described hereinin a way that appears centralized from a logical perspective.

Those skilled in the art will also appreciate that embodiments hereinfurther include a corresponding computer program. The computer programcomprises instructions which, when executed on at least one processor ofan assignment controller 160, cause the controller 160 to carry out anyof the processing described above. Embodiments further include a carriercontaining such a computer program. This carrier may comprise one of anelectronic signal, optical signal, radio signal, or computer readablestorage medium.

FIG. 9 for example illustrates a computer program comprising one or morecode modules contained in memory 1120 of the assignment controller 160in FIG. 8. The code modules include a code module 1300 for identifyingmultiple instances 210 ₁ . . . 210 _(A) of an IMS control function asbeing candidates for assigning to the IMS endpoint 110. The code modulesalso include a module 1310 for obtaining a performance metric for eachcandidate instance 210 ₁ . . . 210 _(A) and a module 1320 for obtainingan emission metric for each candidate instance 210 ₁ . . . 210 _(A), asdescribed above with respect to FIG. 2. The code modules further includea module 1330 for prioritizing the candidate instances 210 ₁ . . . 210_(A) relative to one another based on the performance and emissionmetrics of each instance. Finally, the code modules include a module1340 for controlling assignment of one of the candidate instances to theIMS endpoint 110 to be performed according to this prioritization.

Those skilled in the art will further recognize that, although describedherein with respect to IMS, embodiments herein are equally applicable inany type of cloud communications platform or other framework fordelivering IP multimedia services, even those that do not have adedicated datagram path.

The present invention may, therefore, be carried out in other ways thanthose specifically set forth herein without departing from essentialcharacteristics of the invention. The present embodiments are to beconsidered in all respects as illustrative and not restrictive, and allchanges coming within the meaning and equivalency range of the appendedclaims are intended to be embraced therein.

ABBREVIATIONS

-   AS Application Server-   DHCP Dynamic Host Configuration Protocol-   DNS Domain Name Server-   FQDN Fully Qualified Domain Name-   HSS Home Subscriber Server-   IMS Internet Protocol Multimedia Subsystem-   I-CSCF Interrogating Call Session Control Function-   IP Internet Protocol-   MGCF Media Gateway Controller Function-   MRFC Media Resource Function Controller-   P-CSCF Proxy Call Session Control Function-   S-CSCF Serving Call Session Control Function-   SIP Session Initiation Protocol

What is claimed is:
 1. A method for governing the assignment of an IPMultimedia Subsystem, IMS, control function instance to an IMS endpoint,the method comprising: identifying multiple instances of an IMS controlfunction as being candidates for assigning to the IMS endpoint;obtaining a performance metric for each candidate instance that is ameasure of the extent to which performance requirements for a signalingpath of an anticipated or ongoing session of the IMS endpoint would bemet if the candidate instance were to be assigned to the IMS endpoint;obtaining an emission metric for each candidate instance that is ameasure of the extent to which the candidate instance would producegreenhouse gas emissions if the candidate instance were to be assignedto the IMS endpoint, given the energy consumption and rate of greenhousegas emissions currently attributable to the candidate instance, saidconsumption and rate being dependent on the type of each energy sourcecurrently being used by the candidate instance; prioritizing thecandidate instances relative to one another based on the performance andemission metrics of each instance, by more highly prioritizing candidateinstances that would yield higher performance and lower emissions; andcontrolling assignment of one of the candidate instances to the IMSendpoint to be performed according to said prioritization.
 2. The methodof claim 1, wherein said controlling comprises manipulatingendpoint-specific configuration data that governs said assignment toreflect said prioritization.
 3. The method of claim 2, wherein saidmanipulating comprises manipulating the endpoint-specific configurationdata as maintained by at least one of a home subscriber server, HSS, adynamic host configuration protocol, DHCP, server, a domain name server,DNS, and a policy server.
 4. The method of claim 1, wherein the methodis performed periodically or occasionally in anticipation of thesession.
 5. The method of claim 1, wherein at least one of: saidassignment is performed during a discovery process in which the IMSendpoint attempts to discover the IMS control function, and the methodis performed at least in part before said discovery process; or saidassignment is performed during a registration process in which the IMSendpoint registers with an IMS, and the method is performed at least inpart before said registration process.
 6. The method of claim 1, whereinthe session is an ongoing session, wherein two or more of the candidateinstances are virtual instances of the IMS control function in avirtualized IMS, wherein assignment of one of the candidate instances tothe IMS endpoint comprises changing the instance assigned to the IMSendpoint from an old virtual instance to a new virtual instance andmigrating a state of the old virtual instance to a state of the newvirtual instance to preserve service continuity.
 7. The method of claim6, wherein said controlling comprises triggering an IMS managementsystem to perform said assignment according to said prioritization. 8.The method of claim 1, wherein obtaining the emission metric for acandidate instance comprises determining the rate of greenhouse gasemissions currently attributable to the candidate instance in accordancewith a defined policy, wherein the policy effectively defines differentpossible rates attributable to the candidate instance depending oncertain conditions, wherein the policy specifies those conditions interms of at least one of: different times of day; different locations ofthe hardware executing the instance; different types of one or moreenergy sources used by the candidate instance; different types of mediafor the session; and different durations of the session.
 9. The methodof claim 1, wherein the performance metric for a candidate instance is,at least in part, a measure of the extent to which signaling delayrequirements for the signaling path would be met if the candidateinstance were to be assigned to the IMS endpoint, said delayrequirements being dependent on a location of the instance relative tothe current location of the IMS endpoint.
 10. The method of claim 1,further comprising obtaining a billing parameter that indicates whetherand/or to what extent the IMS endpoint is subscribed to a serviceproviding said prioritized assignment, and determining whether or towhat extent to perform the method based on the billing parameter. 11.The method of claim 1, wherein said prioritizing is further based onhistorical data indicating which of the candidate instances haveactually been assigned to the same or a different IMS endpoint in thepast.
 12. The method of claim 1, wherein the IMS control function iseither a proxy call session control function, P-CSCF, a serving callsession control function, S-CSCF, an interrogating proxy session controlfunction, I-CSCF, a media resource function controller, MRFC, or a mediagateway controller function, MGCF.
 13. The method of claim 1, wherein:the IMS control function is a first IMS control function; the methodfurther comprises identifying multiple instances of a second IMS controlfunction as being candidates for assigning to the IMS endpoint incombination with the first IMS control function; obtaining a performancemetric comprises obtaining a performance metric for each combination ofcandidate instances of the first and second IMS control functions thatis a measure of the extent to which performance requirements for thesignaling path would be met if the candidate instances were to beassigned to the IMS endpoint in combination; obtaining an emissionmetric comprises obtaining an emission metric for each combination ofcandidate instances of the first and second IMS control functions thatis a measure of the extent to which the candidate instances incombination would produce greenhouse gas emissions if the candidateinstances were to be assigned to the IMS endpoint in combination, giventhe energy consumption and rate of greenhouse gas emissions currentlyattributable to that combination, said consumption and rate being acombination of the respective rates currently attributable to thecandidate instances individually; said prioritizing comprisesprioritizing combinations of candidate instances of the first and secondIMS control functions relative to one another based on the performanceand emission metrics of each combination; and said controlling comprisescontrolling assignment of one of the combinations to the IMS endpoint tobe performed according to said prioritization.
 14. The method of claim13, wherein the first IMS control function is a serving call sessioncontrol function, S-CSCF, and the second IMS control function is eithera proxy call session control function, P-CSCF, a media resource functioncontroller, MRFC, or a media gateway controller function, MGCF.
 15. Anassignment controller for governing the assignment of an IP MultimediaSubsystem (IMS) control function instance to an IMS endpoint, theassignment controller comprising: processing circuitry and memory, thememory containing instructions executable by the processing circuitrywhereby the assignment controller is configured to: identify multipleinstances of an IMS control function as being candidates for assigningto the IMS endpoint; obtain a performance metric for each candidateinstance that is a measure of the extent to which performancerequirements for a signaling path of an anticipated or ongoing sessionof the IMS endpoint would be met if the candidate instance were to beassigned to the IMS endpoint; obtain an emission metric for eachcandidate instance that is a measure of the extent to which thecandidate instance would produce greenhouse gas emissions if thecandidate instance were to be assigned to the IMS endpoint, given theenergy consumption and rate of greenhouse gas emissions currentlyattributable to the candidate instance, said consumption and rate beingdependent on the type of each energy source currently being used by thecandidate instance; prioritize the candidate instances relative to oneanother based on the performance and emission metrics of each instance,by more highly prioritizing candidate instances that would yield higherperformance and lower emissions; and control assignment of one of thecandidate instances to the IMS endpoint to be performed according tosaid prioritization.
 16. The assignment controller of claim 15, whereinthe assignment controller is distributed over multiple IMS domains. 17.The assignment controller of claim 15, wherein the assignment controllercomprises: a management interface configured to receive a provisioningrequest from an IMS management system for provisioning a service forsaid prioritized assignment; a session initiation protocol, SIP,interface configured to communicate with one or more serving callsession control functions, S-CSCFs; and a Diameter interface configuredto communicate with a home subscriber server, HSS.
 18. The assignmentcontroller of claim 15, the memory containing instructions executable bythe processing circuitry whereby the assignment controller is configuredto manipulate endpoint-specific configuration data that governs saidassignment to reflect said prioritization.
 19. The assignment controllerof claim 18, the memory containing instructions executable by theprocessing circuitry whereby the assignment controller is configured tomanipulate the endpoint-specific configuration data as maintained by atleast one of a home subscriber server, HSS, a dynamic host configurationprotocol, DHCP, server, a domain name server, DNS, and a policy server.20. The assignment controller of claim 15, the memory containinginstructions executable by the processing circuitry whereby theassignment controller is configured to perform said identifying, saidobtaining of the performance metric, said obtaining of the emissionmetric, said prioritizing, and said controlling periodically oroccasionally in anticipation of the session.
 21. The assignmentcontroller of claim 15, wherein at least one of: said assignment isperformed during a discovery process in which the IMS endpoint attemptsto discover the IMS control function, and the assignment controller isconfigured to perform said identifying, said obtaining of theperformance metric, said obtaining of the emission metric, saidprioritizing, and said controlling at least in part before saiddiscovery process; or said assignment is performed during a registrationprocess in which the IMS endpoint registers with an IMS, and the methodis performed at least in part before said registration process.
 22. Theassignment controller of claim 15, wherein the session is an ongoingsession, wherein two or more of the candidate instances are virtualinstances of the IMS control function in a virtualized IMS, whereinassignment of one of the candidate instances to the IMS endpointcomprises changing the instance assigned to the IMS endpoint from an oldvirtual instance to a new virtual instance and migrating a state of theold virtual instance to a state of the new virtual instance to preserveservice continuity.
 23. The assignment controller of claim 22, thememory containing instructions executable by the processing circuitrywhereby the assignment controller is configured to trigger an IMSmanagement system to perform said assignment according to saidprioritization.
 24. The assignment controller of claim 15, the memorycontaining instructions executable by the processing circuitry wherebythe assignment controller is configured to determine the rate ofgreenhouse gas emissions currently attributable to the candidateinstance in accordance with a defined policy, wherein the policyeffectively defines different possible rates attributable to thecandidate instance depending on certain conditions, wherein the policyspecifies those conditions in terms of at least one of: different timesof day; different locations of the hardware executing the instance;different types of one or more energy sources used by the candidateinstance; different types of media for the session; and differentdurations of the session.
 25. The assignment controller of claim 15,wherein the performance metric for a candidate instance is, at least inpart, a measure of the extent to which signaling delay requirements forthe signaling path would be met if the candidate instance were to beassigned to the IMS endpoint, said delay requirements being dependent ona location of the instance relative to the current location of the IMSendpoint.
 26. The assignment controller of claim 15, the memorycontaining instructions executable by the processing circuitry wherebythe assignment controller is configured to obtain a billing parameterthat indicates whether and/or to what extent the IMS endpoint issubscribed to a service providing said prioritized assignment, anddetermine whether or to what extent to perform said identifying, saidobtaining of the performance metric, said obtaining of the emissionmetric, said prioritizing, and said controlling based on the billingparameter.
 27. The assignment controller of claim 15, wherein the memorycontaining instructions executable by the processing circuitry wherebythe assignment controller is configured to prioritize the candidateinstances further based on historical data indicating which of thecandidate instances have actually been assigned to the same or adifferent IMS endpoint in the past.
 28. The assignment controller ofclaim 15, wherein the IMS control function is either a proxy callsession control function, P-CSCF, a serving call session controlfunction, S-CSCF, an interrogating proxy session control function,I-CSCF, a media resource function controller, MRFC, or a media gatewaycontroller function, MGCF.
 29. The assignment controller of claim 15,wherein the IMS control function is a first IMS control function, andwherein the memory containing instructions executable by the processingcircuitry whereby the assignment controller is configured to: identifymultiple instances of a second IMS control function as being candidatesfor assigning to the IMS endpoint in combination with the first IMScontrol function; obtain a performance metric for each combination ofcandidate instances of the first and second IMS control functions thatis a measure of the extent to which performance requirements for thesignaling path would be met if the candidate instances were to beassigned to the IMS endpoint in combination; obtain an emission metricfor each combination of candidate instances of the first and second IMScontrol functions that is a measure of the extent to which the candidateinstances in combination would produce greenhouse gas emissions if thecandidate instances were to be assigned to the IMS endpoint incombination, given the energy consumption and rate of greenhouse gasemissions currently attributable to that combination, said consumptionand rate being a combination of the respective rates currentlyattributable to the candidate instances individually; prioritizecombinations of candidate instances of the first and second IMS controlfunctions relative to one another based on the performance and emissionmetrics of each combination; and control assignment of one of thecombinations to the IMS endpoint to be performed according to saidprioritization.
 30. The assignment controller of claim 15, wherein thefirst IMS control function is a serving call session control function,S-CSCF, and the second IMS control function is either a proxy callsession control function, P-CSCF, a media resource function controller,MRFC, or a media gateway controller function, MGCF.
 31. A non-transitorycomputer-readable storage medium having stored thereon a computerprogram that, when executed by a processor of an assignment controller,causes the assignment controller to perform a process for governing theassignment of an IP Multimedia Subsystem (IMS) control function instanceto an IMS endpoint, wherein the process comprises: identifying multipleinstances of an IMS control function as being candidates for assigningto the IMS endpoint; obtaining a performance metric for each candidateinstance that is a measure of the extent to which performancerequirements for a signaling path of an anticipated or ongoing sessionof the IMS endpoint would be met if the candidate instance were to beassigned to the IMS endpoint; obtaining an emission metric for eachcandidate instance that is a measure of the extent to which thecandidate instance would produce greenhouse gas emissions if thecandidate instance were to be assigned to the IMS endpoint, given theenergy consumption and rate of greenhouse gas emissions currentlyattributable to the candidate instance, said consumption and rate beingdependent on the type of each energy source currently being used by thecandidate instance; prioritizing the candidate instances relative to oneanother based on the performance and emission metrics of each instance,by more highly prioritizing candidate instances that would yield higherperformance and lower emissions; and controlling assignment of one ofthe candidate instances to the IMS endpoint to be performed according tosaid prioritization.